.TH "AUDIT_ADD_RULE_DATA" "3" "Aug 2009" "Red Hat" "Linux Audit API"
.SH NAME
audit_add_rule_data \- Add new audit rule
.SH "SYNOPSIS"
.B #include <libaudit.h>
.sp
int audit_add_rule_data(int fd, struct audit_rule_data *rule, int flags, int action);

.SH "DESCRIPTION"

audit_add_rule_data adds an audit rule previously constructed with audit_rule_fieldpair_data(3) to one of several kernel event filters. The filter is specified by the flags argument. Possible values for flags are:

.TP 3
\(bu
AUDIT_FILTER_USER - Apply rule to userspace generated messages. This is the user filter. Normally all user space originating events are accepted. Rules on this filter are typically written to block specific events.
.TP
\(bu
AUDIT_FILTER_TASK - Apply rule at task creation (not syscall). This is the task filter. It's normally used to exclude an application from being audited.
.TP
\(bu
AUDIT_FILTER_EXIT - Apply rule at syscall exit. This is the main filter that is used for syscalls and filesystem watches. Normally all syscall do not trigger events, so this is normally used to specify events that are of interest.
.TP
\(bu
AUDIT_FILTER_EXCLUDE - Apply rule at audit_log_start. This is the exclude filter which discards any records that match.  The action type is ignored for this filter, defaulting to "never".
.LP
.TP
\(bu
AUDIT_FILTER_FS - Apply rule when adding PATH auxiliary records to SYSCALL events. This is the filesystem filter. This is used to ignore PATH records that are not of interest.
.LP

.PP
The rule's action has two possible values:

.TP 3
\(bu
AUDIT_NEVER - Do not build context if rule matches.
.TP
\(bu
AUDIT_ALWAYS - Generate audit record if rule matches.
.LP

.SH "RETURN VALUE"

The return value is <= 0 on error, otherwise it is the netlink sequence id number. This function can have any error that sendto would encounter.

.SH "SEE ALSO"

.BR audit_rule_fieldpair_data (3),
.BR audit_delete_rule_data (3),
.BR auditctl (8).

.SH AUTHOR
Steve Grubb.
